Pre-flight system for PDF/VT

ABSTRACT

A method for validating a splitting operation accesses a document and a catalog tree. The method selects a subset of the total pages in the document. The method splits a section of branches from the catalog tree using a splitter in a user device. Each branch corresponds to a page included in the subset. The method processes the subset using the branches to generate split output pages. The method analyzes each split output page to determine if the file split correctly. In response to a split failure, the method determines if the split failure is related to one of a structure error and a metadata syntax error. In response to a correct split, the method provides the print job to an associated output device in communication with the user device.

BACKGROUND

The present disclosure relates to a system and a method that determineswhether a file will split correctly on a print server and, morespecifically, a system that diagnoses a source of the split failure.

Portable Document Format (“PDF”) is a commonly used standard forrepresenting a finished document as fixed content after the document isformatted. A PDF/VT file is a type of PDF file for exchange of variabledata and transactional (VT) printing. Generally, the fixed contentportion of the PDF functions as a template that can be used in multiplerenderings. Each rendering process undergoes a merge with variable datafor providing printout or display output with variable content.

In a conventional approach, the PDF/VT file is processed at a printerdevice, which splits the document into chunks, raster image processes(“RIPs”) the chunks, and reassembles the pages from the chunks intocorrect order for rendering the output. Mainly, the PDF/VT file isdivided into multiple chunks using a splitter located at the printerdevice.

The PDF/VT file can include a catalog tree, known as a Dpart catalog,which contains metadata for the variable rendering of contents definedwithin the PDF pages. An accompanying Job Definition Format (“JDF”) jobticket includes directions for how the metadata is to be used.

The printer-based splitter splits the document based on how the catalogtree is built. In other words, the document is split according to howthe catalog tree interacts with the splitter technology. An error canoccur when the document splits incorrectly. For a conventional printnetwork and/or device, the fault handling system ceases processing ofthe print job when the error occurs. The fault handling system does notprovide any explanation indicating why the printer ceases to completeprocessing of the print job. Although, embodiments are contemplatedwhere the printer continues to RIP the print job and reassemble thepages in the incorrect order.

When an error occurs, a user can be inconvenienced by a stalled and/orceased print job and/or by the task of resending the print instructionto a different printer device. Therefore, the user may not want tocommit to printing a long file until it has confidence in the printoutcome.

Because various types of printer devices include different splitterembodiments, which can each interact with a DPart hierarchy differently,a system and method are desired which can verify that the splitter canproperly split the document before the processing is initiated at theprinter device. In this manner, a verification process is desired thatreduces the faults that are later caused by errors in a conventionalsplitting operation.

BRIEF DESCRIPTION

One embodiment of the disclosure relates to a method for validatingsplitting of a document using a particular output device technology. Themethod includes accessing at a client computer a file representing apreviously created document. The method includes accessing a catalogtree residing in the document and including metadata corresponding witha job ticket embedded in the file for rendering the document. The methodincludes selecting a subset of the total pages in the document. Themethod includes splitting a section of branches from the catalog treeusing a splitter in a user device. Each branch corresponds to a pageincluded in the subset. The method includes processing the subset usingthe branches to generate split output pages. The method includesanalyzing each split output page to determine if the file splitcorrectly. In response to a split failure, the method includesdetermining if the split failure is related to one of a structure errorand a metadata syntax error. In response to a correct split, the methodincludes providing the print job to an associated output device incommunication with the user device.

Another embodiment of the disclosure relates to a system for validatingsplitting of a document using a particular output device technology. Thesystem includes a user device. The user device includes comprising asplitter based on a model of an output device in communication with theuser device. The splitter splits a section of branches. Each branchcorresponds with a page included in a subset of total pages in adocument. The user device includes a subset validation module thatprocesses the subset using the branches to generate split output pages.The subset validation module analyzes each split output page todetermine if the file split correctly. In response to a split failure,the subset validation module determines if the split failure resultsfrom one of a structure error and a metadata syntax error. In responseto a correct split, the subset validation module provides the print jobto an associated output device in communication with the user device.The user device includes a memory which stores the modules and aprocessor, in communication with the memory, for executing the modules.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a general overview of a method for determining a proper splitoperation according to the present embodiment.

FIG. 2 is a schematic illustration of a system in one aspect of theexemplary embodiment.

FIG. 3 is a flow chart illustrating a pre-flight process for validatinga file according to the exemplary embodiment.

FIG. 4 is a flow chart illustrating an exemplary method for determininga type of split error according to the exemplary embodiment.

FIG. 5 is a flow chart illustrating an exemplary method for generating arepresentation simulating a split PDF/VT document.

DETAILED DESCRIPTION

The present disclosure relates to a system and a method that determineswhether a file will split correctly on a print server. FIG. 1 is ageneral overview of a method 10 for determining a proper splitoperation. In the contemplated embodiment, the system analyzes theprinter-based splitter capability at a client device. In response to auser selecting an application on a graphic user interface, the method isinitiated. The method starts at S12. The client device accesses adocument at S14. At S16, the client device accesses a catalog tree thatcontains metadata for the variable rendering of content defined withinthe PDF pages. A client-based splitter produces a subset of possiblechunks at various split boundaries at S18. Mainly, at least one sampleis selected from the total pages in the document. Similarly, theclient-based splitter splits a section of branches from the catalog treeat S20. Each branch corresponds with a page in the subset. The resultantchunks are analyzed to determine if the correct output is within thechunks at S22. Using the analysis results, the system determines whetherthe subset split correctly at S24. A correct split, at the subset level,is indicative that the document will split correctly at theprinter-based splitter. In response to the subset splitting incorrectly(NO at S26), a fault is raised at S28. The system identifies a reasonfor the failure at S30. In response to the subset splitting correctly(YES at S26), the client device provides the print job to an associatedDFE for processing at S32. The method ends at S34.

FIG. 2 is a functional block diagram of a pre-flight system 100 in oneexemplary embodiment. The pre-flight system 100 may include a splitterverification system 102, hosted by a computing device 104, such as aclient computer and/or device, and a print job processing system 106,hosted by a digital front end (“DFE”), such as the illustrated printerand/or output device 108, which are linked together by communicationlinks 110, referred to herein as a network. These components aredescribed in greater detail below.

The splitter verification system 102 illustrated in FIG. 2 includes aprocessor 112, which controls the overall operation of the system 102 byexecution of processing instructions, which are stored in memory 114connected to the processor 112.

The splitting and verification operation disclosed herein is performedby the processor 112 according to the instructions stored in the memory114. In particular, the memory 114 stores a subset validation module116, a structure determination module 118, a syntax determination module120, and an output determination module 122.

The subset validation module 116 selects a sub-sample from the totalpages of the document for splitting by a client-based splitter 124. Themodule 116 also identifies branches from a catalog tree, for splittingby the client-based splitter, that each corresponds to a page in thesub-sample. The module 116 further determines whether the catalog treemeets criteria of the printer-based splitter at the DFE.

When an error occurs, the structure determination module 118 determinesif the fault resulted from a structure error. The module 118 determinesif the number of split pages equals the number of branches. In responseto unequal numbers of split pages and branches, the module 118determines at least one branch that is incorrectly assembled.

Similarly, when an error occurs, the syntax determination module 120determines whether commands in the DPart catalog fit the printer-basedsplitter model located in the output device.

An output determination module 122 generates a modified displayrepresentation to simulate the output by overwriting the media boxinformation in the PDF and using the metadata to determine the finaldimensions.

These modules 116-122 will be later described with reference to theexemplary method.

The splitter verification system 102 also includes one or morecommunication interfaces (I/O), such as network interfaces 126 forcommunicating with external devices, such as output device 108. Thevarious hardware components 112, 114, (random access memory “RAM”) 128of the client device 104 may all be connected by a bus 130.

With continued reference to FIG. 2, the splitter verification system 102is communicatively linked to a user interface device (GUI) 132 via awired and/or wireless link. In various embodiments, the user interfacedevice 132 may include one or more of a display device, for displayinginformation to users, and a user input device, such as a keyboard ortouch or writable screen, for inputting instructions and/or receivingstatus information, and/or a cursor control device, such as a mouse,trackball, or the like, for communicating user input information andcommand selections to the processor 112. Specifically, the userinterface device 132 includes at least one of an input device and anoutput device, both of which include hardware, and which arecommunicatively linked with the client device 104 via wired and/orwireless link(s).

With continued reference to FIG. 2, the splitter verification system 102includes a client-based splitter 124 that is part of or in communicationwith the client device 104. The client-based splitter 124 is adapted toaccess the catalog tree 136 from within the PDF/VT document 134 andsplit the tree into multiple branches, split the PDF/VT document intomultiple chunks, and reassemble (reassert) each branch with (within) itscorresponding PDF/VT chunk. The chunks, including embedded branchinformation, can be streamed to the DFE 108 as a package 130.

The splitter verification system 102 verifies that a printer-basedsplitter can interpret the DPart catalog by splitting and analyzing asub-sample of pages that undergo a splitter operation using aclient-based splitter having knowledge and/or functionality of theprinter-based splitter. The client-based splitter is a representation ofthe splitter on the printer system 106. The system 102 outputs one of averification and notification 138 indicating whether the catalog treemeets criteria of the print-based splitter based on the correct orincorrect split outcome.

As mentioned, the client device 104 of the pre-flight system 100 iscommunicatively linked with the DFE 108 via link 110. In response to acorrect split, the DFE 108 receives the print job and processes it togenerate a display and/or output 140. While the DFE may include anelectronic display, for example as part of a graphic user interface 142,the exemplary embodiment includes an image rendering device that mayinclude a marking engine 144, which applies marking medium, such as inkor toner, to a substrate, such as paper, using, for example, a laser,inkjet, thermal, or other transfer process. The printer renders imageson print media, such as paper, and can be a copier, laser printer,bookmaking machine, facsimile machine, or a multifunction machine (whichincludes one or more functions such as scanning, printing, archiving,emailing, and faxing.

The memory 114, 128 may represent any type of tangible computer readablemedium such as random access memory (RAM), read only memory (ROM),magnetic disk or tape, optical disk, flash memory, or holographicmemory. In one embodiment, the memory 114, 128 may each comprise acombination of random access memory and read only memory. The digitalprocessor 112 can be variously embodied, such as by a single-coreprocessor, a dual-core processor (or more generally by a multiple-coreprocessor), a digital processor and cooperating math coprocessor, adigital controller, or the like. The digital processor 112, in additionto controlling the operation of the respective splitter verificationsystem 102, executes instructions stored in memory 114 for performingthe parts of the method outlined below.

The software modules as used herein, are intended to encompass anycollection or set of instructions executable by the splitterverification system 102 so as to configure the computer or other digitalsystem to perform the task that is the intent of the software. The term“software” as used herein is intended to encompass such instructionsstored in storage medium such as RAM, a hard disk, optical disk, or soforth, and is also intended to encompass so-called “firmware” that issoftware stored on a ROM or so forth. Such software may be organized invarious ways, and may include software components organized aslibraries, Internet-based programs stored on a remote server or soforth, source code, interpretive code, object code, directly executablecode, and so forth. It is contemplated that the software may invokesystem-level code or calls to other software residing on the server orother location to perform certain functions.

The communication interface(s) 126 may include, for example, a modem, arouter, a cable, and/or Ethernet port, etc.

As will be appreciated, while two computing devices 104, 108 areillustrated by way of example, the system 100 may be hosted by fewer ormore linked computing devices. Each computing device may include, forexample, a server computer, desktop, laptop, or tablet computer,smartphone or any other computing device capable of implementing themethod described herein.

FIG. 3 is a flow chart illustrating an exemplary method 300 forvalidating a file according to one embodiment. In the discussedembodiment, the file is a PDF/VT document file including a PDF/VTdocument, catalog tree, and accompanying job ticket. The method startsat S302.

In the contemplated embodiment, a splitter application is packaged foruse on client compute platforms. In response to a user-input selectingthe application at S304, the pre-flight process is initiated at theclient device at S306. In another contemplated embodiment, thepre-flight application can run on the DFE/printer device, thus removingthe need to receive status information transmitted from the DFE.

A subset validation module selects at least one subset of pages from thedocument at S308. Mainly, the subset functions as a sample of the entiredocument. By splitting and analyzing the subset at the client device,the system can predict results of a full split of the entire document atthe DFE. Therefore, the pre-flight process can be performed in a clientcomputing environment to ascertain whether the file will split properlyat the DFE before the file is transmitted to the DFE. In other words,the split output that is generated from the subset can be used todetermine whether split output for the full document will RIP and/orprint as expected at the printer device.

Accordingly, a subset of the total pages is selected to ascertain if thedocument will split correctly and, in instances where the subset splitsincorrectly, to identify a cause and/or a remedy for the faultcondition.

A client-based splitter splits the subset into chunks at S310. Theapplication has knowledge of the splitter model and technology used bythe printer-based splitter. Accordingly, the client-based splittersplits the subset in the same manner. The client-based splitter is runwith different split lengths to determine a validity of the splitoutput. In other words, the client-based splitter can split the subseton different cadences of pages. In one embodiment, predetermined splitlengths can be configured by a user via selections made at the graphicuser interface. The different split lengths ensure that the split chunkscontain page contents across set boundaries. Therefore, the system candetermine how any of the splits that cross set boundaries can causeproblems.

More specifically, by using different split lengths, the system candetermine if the catalog tree splits accurately. Pages are split basedon how a catalog tree, associated with the file, interacts with splittertechnology. Therefore, pages may not split correctly if the DParthierarchy is constructed in a way that cannot interact with theparticular model of a printer-based splitter. The client-based splitterthan splits the catalog tree into a number of branches at S312. Mainly,at least the portion of the catalog tree that corresponds with thesubset is split into a number of branches, each associated with a pagein the subset.

Continuing with FIG. 3, the split output pages are scanned at S314. Thepurpose of the scan is to determine if each page has an associated DPartcatalog at S316. In response to the number of branches matching thenumber of split output pages (YES at S316), the system determines thatthe document file will split correctly at the printer network and/ordevice at S318. The system can provide a notification indicating thatthe document is validated at S320.

In response to the number of branches does not match the number of splitoutput pages (NO at S316), the system determines that the catalog treeis formed incorrectly at S322. The system raises a fault message atS324. The fault message notifies a user that the document will not splitcorrectly at the printer network and/or device. This notification is anerror message that indicates to a user that the catalog tree associatedwith the PDF/VT document does not meet the criteria of the printer-basedsplitter in the printer network and/or device. The fault message caninclude the erroneous pages to assist in debugging.

In another contemplated embodiment (not shown), the system can determineif the number of branches is greater than or equal to the number ofpages. For the number of branches being greater than or equal to thenumber of pages, the system determines that the document file will splitcorrectly at the printer network and/or device at S318. In other words,the tree can split correctly if the number of branches is larger thanthe number of pages. For the number of branches being fewer than thenumber of pages, the system determines that the catalog tree is formedincorrectly.

In summary, the method described for FIG. 3 analyzes a catalog tree todetermine if it meets criteria for the printer-based splitter. Themessages at S320 and S324 verify that the catalog tree has beenanalyzed. In the disclosed embodiment, a later discussed error analysisis also performed at S326. The method ends at S328.

The system is adapted to raise faults and/or warnings for indicatingthat the printing device is not capable of handling either the metadata,the media and/or finishing calls. Mainly, the semantic and structureinformation is contained within a configuration file. Therefore, anerror analysis is performed to determine which one of the semantic andstructure information is resulting in the error.

FIG. 4 is a flow chart illustrating an exemplary method 400 forperforming an error analysis according to one embodiment. The methodstarts at S402. The error analysis more specifically includes a metadataanalysis, which can be used to obtain finishing and media statusinformation from the printer device via an Internet Printing Protocol(“IPP”).

The syntax determination module performs an analysis to determine asemantic layout of the catalog tree at S404. The module 120 scans themetadata at S406. The scanned metadata is analyzed to determine if itmatches the semantics and the structure defined in the PDF/VTspecification at S408. In other words, the module 120 determines ifcommands in the catalog tree fit the model of the output device at S408.The system searches for text that it might expect in the catalog treeassociated with particular finishing or media structure instructions,such as a type of landscape. The system expects the command to beincluded in the catalog tree in a certain semantic layout. If thecommand does not meet the expected layout (NO at S410), it determinesthat the printer device cannot (i.e., will not) understand the commandat S412. The system provides a notification indicating that the syntaxin the tree structure is incorrect at S414. In one illustrative example,for metadata that contains “StapleLocation RightDualLandscape”, awarning and/or fault can be displayed which declares that the particularsyntax is not supported on the printer network and/or device. For acommand that does meet a syntax layout expected by the printer device(YES at S410), the system determines that the fault is not based on asyntax error at S416. The method can, in one embodiment, determine ifthe error is (rather) a structure-based error at S420. Thisdetermination S420 can be made in parallel with, or in response to, thesemantic layout analysis at S404.

The system determines if the fault is being caused by a structure errorat S420. Mainly, the structure determination module analyzes the catalogtree to determine how the branches are assembled at S422. The analysisis used to determine where the branches are assembled incorrectly, i.e.,e.g., perhaps whether a branch is assembled at the wrong level, i.e., upor down a level. At S424, the module 118 identifies at least one pagethat is associated with an incorrectly assembled branch. At S426, thesystem provides notification that the tree structure is incorrect.Mainly, notification indicates that the portion of the catalog treecorresponding to the page number does not meet the criteria of thesplitter.

In yet another embodiment, the notification can indicate the problem inthe catalog tree and/or instruct the user on how to remedy it at S428.

For example, for a structural command that associates a location of afinishing option that cannot be completed by the printer device, thenotification can indicate that the printer device is expecting metadatathat identifies in the structure a type and/or model of the device. Forexample, if the structure is “DPM>HP>Staple 1>StapleLocation SinglePortrait” raises a warning and/or fault, the message can state thatprinter device is expecting the structure to be DPM>Xerox>Staple1>StapleLocation Single Portrait. DPM stands for DPart metadata a PDF/VTconcept. The method ends at S430.

FIG. 5 shows another aspect of the disclosure, being a flow chartillustrating an exemplary method 500 for generating an electronicrepresentation simulating a split PDF/VT document. The method starts atS402. Using the metadata information within the print job and the IPPstatus information, a visual simulation of the PDF/VT is performed for aselected print system.

In other words, the method 500 of FIG. 5 is performed to provide theuser with a digital output simulation, thus enabling the user tovisually validate whether the DFE and/or print device 108 can produce aprinted output of the PDF/VT including all of the preselectedoperations. For illustrative purposes, an example includes when selectprint/finishing selections, such as a portrait landscape and/or dualstaples, is included within the metadata, the system 100 determines ifthe particular DFE/print device 108 can generate the print result. Inanother illustrative example, the finishing metadata may require thatthe output be printed short edge feed (“SEF”). And, by this, the mediabox and page rotation are appropriately updated for the system 100 toprovide a visual representation of the expected print result (of whichit is capable of rendering).

To do this, the output determination module 122 must overwrite the mediabox information in the PDF at S504. The media size metadata informationis used to overwrite the media box information in the PDF. The metadatais used by the module 122 to determine the final media box dimensions atS506. The module updates the media box and page information in the PDFto include the final media box dimensions that was extracted and/orretrieved from the metadata at S508. The metadata information (such as,e.g., the media color) is written into the PDF via an addition of atransparent background fill that covers the entire media box. Thetransparent fill color is determined by a table converting the metadatasyntax (e.g., blue) into RGB values (e.g., 0, 0, 100).

The updated media box and page information is used to generate amodified display representation, which simulates the output at S510. Inother words, the finished metadata is used to add a visualrepresentation. For example, images (of the front side of a staple andthe backside of a staple) are added to the PDF for the first page andlast page of a stapled set. The resultant PDF can be viewable inAcrobat.

At S512, the output determination module 122 extracts and analyses themetadata to ascertain whether it can meet the printer device'sspecifications. By this, the module 122 determines whether the printerdevice has the capabilities to render an output according to theparticular instructions in the metadata. As part of this analysis, themodule 122 generates a digital representation using the extractedmetadata. In response to the digital representation meeting the device'sspecifications (YES at S514), the method ends at S518. In response tothe digital representation not meeting the device's specifications (NOat S514), the system provides an error notification to the user at S416.The method ends at S418.

In a contemplated alternate embodiment to be performed concurrently withor alternately from the electronic representation, the system can testPS setpagedevice commands using a distiller for converting the PSsetpagedevice commands to PDF/VT metadata.

One aspect of the present disclosure includes a system and a method thatdetermines whether a PDF/VT file will split properly on the DFE/printerdevice by splitting a subset of the document at the client device usinga client-based splitter that simulates and/or has knowledge of theprinter-based splitter. By determining if the PDF/VT file will split,the system prevents a system crash and/or hang scenario that may resultfrom a split failure in a conventional system.

Another aspect of the disclosure relates to a system and method thatdetermines if the PDF/VT semantics within the PDF/VT print jobspecification meet the rendering capabilities of the DFE/printer device.As part of this determination process, the system performs an erroranalysis on a subsample that doesn't split properly. For a subsamplethat splits properly, the system generates a visual representation ofthe PDF/VT output, including media color, media size, orientation, andfinishing.

Yet another aspect of the disclosure includes providing a user with anoption for selectively initiating the application. The system providesthe client device with the application, which estimates solutions formetadata and syntax errors.

Although the control methods 10, 300, 400 are illustrated and describedabove in the form of a series of acts or events, it will be appreciatedthat the various methods or processes of the present disclosure are notlimited by the illustrated ordering of such acts or events. In oneembodiment, in FIG. 4, a comparison can be performed first on thesemantic information before the structure information. In this regard,except as specifically provided hereinafter, some acts or events mayoccur in different order and/or concurrently with other acts or eventsapart from those illustrated and described herein in accordance with thedisclosure. It is further noted that not all illustrated steps may berequired to implement a process or method in accordance with the presentdisclosure, and one or more such acts may be combined. The illustratedmethods and other methods of the disclosure may be implemented inhardware, software, or combinations thereof, in order to provide thecontrol functionality described herein, and may be employed in anysystem including but not limited to the above illustrated system 100,wherein the disclosure is not limited to the specific applications andembodiments illustrated and described herein.

It will be appreciated that variants of the above-disclosed and otherfeatures and functions, or alternatives thereof, may be combined intomany other different systems or applications. Various presentlyunforeseen or unanticipated alternatives, modifications, variations orimprovements therein may be subsequently made by those skilled in theart which are also intended to be encompassed by the following claims.

What is claimed is:
 1. A method for validating splitting of a documentusing a particular output device technology, the method comprising:accessing at a client computer a file representing a previously createddocument; accessing a catalog tree residing in the document andincluding metadata corresponding with a job ticket embedded in the filefor rendering the document; selecting a subset of the total pages in thedocument; splitting a section of branches from the catalog tree using asplitter in a user device, each branch corresponding to a page includedin the subset; processing the subset using the branches to generatesplit output pages; analyzing each split output page to determine if thefile split correctly; in response to a split failure, determining if thesplit failure is related to one of a structure error and a metadatasyntax error; and, in response to a correct split, providing the printjob to an associated output device in communication with the userdevice.
 2. The method according to claim 1 further comprising: splittingat least two sections of branches at different split lengths.
 3. Themethod according to claim 1, wherein the determining the structure errorincludes: scanning the split output pages to determine if each splitoutput page has an associated branch; determining if a number ofbranches equals a number of pages in the subsection; in response to thenumber of branches being not equal to the number of pages, classifyingthe split failure as resulting from a structure error.
 4. The methodaccording to claim 3 further including: in response to classifying thesplit failure as resulting from a structure error, determining at leastone branch that is incorrectly assembled; and, determining a pagecorresponding with the at least one branch; and, providing anotification indicating that the catalog tree does not meet splittercriteria for an associated splitter in the associated output device. 5.The method according to claim 1 further including: for a split failureresulting from a structure error, outputting default message indicatingthat the catalog tree does not meet the splitter criteria.
 6. The methodaccording to claim 1, wherein the splitter in the user device is basedon a model of the output device.
 7. The method according to claim 1,wherein the determining the metadata syntax error includes: analyzing asemantic layout of the catalog tree.
 8. The method according to claim 7,wherein the analyzing the semantic layout includes: determining ifcommands in the section of the catalog tree fit a model of theassociated output device in communication with the user device; and, inresponse to determining that a command in the section of the catalogtree does not meet an expected layout instructed in the metadata,providing a notification to the user.
 9. The method according to claim 1further comprising: extracting the metadata; overwriting defaultinstructions for a display representation of the document in a completeformat; generating a modified display representation using instructionsin the metadata.
 10. The method of claim 9, wherein the format is aPortable Document Format (PDF).
 11. The method according to claim 10,wherein the overwriting the default instructions includes: overwritingmedia box information in the PDF; using the metadata to determine finalmedia box dimensions; updating the media box and page information; and,generating the modified display representation to simulate output. 12.The method of claim 1 further comprising: producing a digitalrepresentation of the document using the metadata; using the digitalrepresentation to determine whether the metadata can be met byspecifications of the associated output device; in response to themetadata not meeting the specifications, providing an errornotification.
 13. The method according to claim 1, further including: inresponse to a split failure, providing an instruction for remedying thefault.
 14. A system for validating splitting of a document using aparticular output device technology, the system comprising: a userdevice comprising: a splitter based on a model of an output device incommunication with the user device, the splitter being adapted to splita section of branches from a catalog tree residing in the document andincluding metadata corresponding with a job ticket embedded in the filefor rendering the document, each branch corresponding to a page includedin a subset of total pages in a document; a subset validation moduleadapted to: process the subset using the branches to generate splitoutput pages, analyze each split output page to determine if the filesplit correctly, in response to a split failure, determine if the splitfailure results from one of a structure error and a metadata syntaxerror, and in response to a correct split, provide the print job to anassociated output device in communication with the user device; a memorywhich stores the modules; and, a processor, in communication with thememory for executing the modules.
 15. The system according to claim 14,further comprising a structure determination module adapted to analyzethe subset for a structure error, the structure determination modulebeing adapted to: scan the split output pages to determine if each splitoutput page has an associated branch; determine if a number of branchesequals a number of pages in the subsection; in response to the number ofbranches being not equal to the number of pages, classify the splitfailure as resulting from the structure error.
 16. The system accordingto claim 15, wherein the structure determination module is furtheradapted to: in response to classifying the split failure as resultingfrom a structure error, determine at least one branch that isincorrectly assembled; and, determine a page corresponding with the atleast one branch; and, provide a notification indicating that thecatalog tree does not meet splitter criteria for an associated splitterin the associated output device.
 17. The system according to claim 14further comprising a syntax determination module adapted to analyze asemantic layout of the catalog tree, the syntax determination modulebeing adapted to: determine if commands in the section of the dpart treefit a model of the associated output device in communication with theuser device; and, in response to determining that a command in thesection of the dpart tree does not meet an expected layout instructed inthe metadata, provide a notification to the user.
 18. The systemaccording to claim 14 further comprising an output determination moduleadapted to: extract the metadata; overwrite default instructions for adisplay representation of the document in a complete format; generate amodified display representation using instructions in the metadata; and,display the modified display representation.
 19. The system according toclaim 18, wherein the output determination module is further adapted to:overwrite media box information in a PDF; use the metadata to determinefinal media box dimensions; update the media box and page information;and, generate the modified display representation to simulate output.20. The system according to claim 18, wherein the output determinationmodule is further adapted to: produce a digital representation of thedocument using the metadata; use the digital representation to determinewhether the metadata can be met by specifications of the associatedoutput device; in response to the metadata not meeting thespecifications, provide an error notification.